[4/4 messagequeue] Add Vitess vschema and two-shard vtcombo suite - #696
Open
behinddwalls wants to merge 1 commit into
Open
[4/4 messagequeue] Add Vitess vschema and two-shard vtcombo suite#696behinddwalls wants to merge 1 commit into
behinddwalls wants to merge 1 commit into
Conversation
This was referenced Sep 8, 2026
behinddwalls
force-pushed
the
preetam/mq-tenant-vitess
branch
from
September 8, 2026 06:03
c9519fb to
10f0140
Compare
behinddwalls
force-pushed
the
preetam/mq-tenant-vitess
branch
from
September 8, 2026 06:06
10f0140 to
0b69e19
Compare
behinddwalls
marked this pull request as ready for review
September 10, 2026 16:30
mnoah1
approved these changes
Sep 10, 2026
## Summary ### Why? The tenant column is the production vindex. Without a VSchema and a two-shard suite, the schema change is unproven on Vitess. ### What? - Add production xxhash VSchema for every queue table keyed on tenant. - Add a vtcombo integration suite that publishes and consumes across two shards (receive loop bound to the test context). Admin CLI tenant flags shipped with the schema PR because ctl/lib SQL is coupled to the new primary keys. ## Test Plan Vitess suite is Docker-based; run with: `./tool/bazel test //test/integration/extension/messagequeue/mysql/vitess:go_default_test --strategy=TestRunner=local` Co-authored-by: Cursor <cursoragent@cursor.com>
behinddwalls
force-pushed
the
preetam/mq-tenant-vitess
branch
from
September 10, 2026 18:57
0b69e19 to
4980b66
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why?
The tenant column is the production vindex. Without a VSchema and a two-shard suite, the schema change is unproven on Vitess.
What?
Admin CLI tenant flags shipped with the schema PR because ctl/lib SQL is coupled to the new primary keys.
Test Plan
Vitess suite is Docker-based; run with:
./tool/bazel test //test/integration/extension/messagequeue/mysql/vitess:go_default_test --strategy=TestRunner=localIssues